Managing Cross-Filtering, Visual Interactions, and Edit Interactions in Power BI

Course: Microsoft Power BI Training

Topic: Managing Cross-Filtering, Visual Interactions, and Edit Interactions

Course Link: Microsoft Power BI Training at JustAcademy

Demo Link: Register for a Free Course Demo

JustAcademy Website: Visit JustAcademy

1. Introduction to Cross-Filtering and Visual Interactions

Power BI reports contain interactive visuals such as bar charts, line charts, cards, tables, maps, slicers, and matrices. These visuals can communicate with one another so that users can explore data without creating a separate report page for every question.

For example, a report may contain a sales-by-region chart, a sales-by-product chart, and a total-sales card. When a user selects a region, the other visuals can update to show information related to that region. This behavior is controlled through visual interactions.

Managing cross-filtering and visual interactions means deciding how one visual affects another, whether the affected visual should filter or highlight its data, and whether an interaction should be disabled entirely.

Learning Objectives

• Understand cross-filtering and cross-highlighting in Power BI.
• Learn how visual interactions work between charts, tables, cards, and slicers.
• Use Edit interactions to control the behavior of individual visuals.
• Understand the difference between filtering, highlighting, and no interaction.
• Configure interactions for meaningful report navigation and analysis.
• Identify common interaction problems and troubleshoot them.
• Apply interaction settings to a practical Power BI report.

2. What Is Cross-Filtering?

Cross-filtering occurs when a selection in one visual restricts the data displayed in another visual. The destination visual displays results based on the selected category or value.

For example, suppose a column chart displays sales by region. Selecting the West region can cause a product table to show only products sold in the West region.

2.1 Example of Cross-Filtering

Consider the following sales data:

If a user selects West in the region chart, the product table can display:

The table responds to the region selection because Power BI applies the selection as a filter to the destination visual.

2.2 Benefits of Cross-Filtering

• Allows users to investigate a category without manually changing filters.
• Helps identify which products, customers, or regions contribute to a result.
• Supports interactive business analysis.
• Reduces the need to create duplicate visuals for every category.
• Makes dashboards and reports more useful for decision-making.

3. What Is Cross-Highlighting?

Cross-highlighting is another interaction behavior in Power BI. Instead of removing unrelated data completely, the destination visual emphasizes the portion associated with the selected data while retaining the context of the remaining data when the visual supports highlighting.

For example, a chart displaying sales by product may show total sales as the full bar and highlight the portion contributed by a selected region. This lets users compare the selected contribution with the overall result.

3.1 Cross-Filtering vs. Cross-Highlighting

Important: Not every visual supports cross-highlighting in the same way. The available interaction options depend on the source visual, destination visual, and report configuration.

4. Understanding Visual Interactions

Visual interactions define how a visual responds when a user selects a data point, category, or value in another visual. Power BI lets report authors configure these relationships individually.

4.1 Common Visual Interaction Scenarios

• Chart to chart: Selecting a region in a column chart filters or highlights a product chart.
• Chart to card: Selecting a category updates a card showing sales for that category.
• Chart to table: Selecting a bar restricts the table to matching records.
• Slicer to chart: Selecting a year in a slicer updates charts that respond to the slicer.
• Table to chart: Selecting a row may filter or highlight related values in a chart.
• Map to chart: Selecting a location can update other visuals containing related geographic data.

4.2 Source Visual and Target Visual

When configuring interactions, distinguish between the visual that initiates the action and the visual that responds to it.

• Source visual: The chart, table, or other visual where the user makes a selection.
• Target visual: The visual whose displayed data changes in response to the selection.

For example, if the user selects the South region in a region chart and the sales card updates, the region chart is the source visual and the sales card is the target visual.

5. Introduction to Edit Interactions

Edit interactions is a Power BI Desktop feature that allows report authors to control how a selected visual affects other visuals on the same report page.

Instead of accepting the default interaction behavior, you can choose the appropriate behavior for each target visual. This is particularly useful when a report contains several charts that should not all respond to every selection.

5.1 Why Edit Interactions Is Important

• Prevents unnecessary changes in unrelated visuals.
• Improves the readability of reports.
• Allows selected visuals to remain independent.
• Supports different analytical workflows on the same page.
• Helps avoid confusing or misleading comparisons.
• Allows report designers to create a more controlled user experience.

5.2 Example

Imagine a report page containing:

• A sales-by-region column chart.
• A sales-by-product bar chart.
• A monthly sales trend line chart.
• A total-sales card.

When a user selects a region, the product chart and total-sales card may need to update. However, the monthly trend chart might be intended to show the overall company trend at all times. Edit interactions can be used to disable the region chart's effect on the trend chart while keeping the other interactions enabled.

6. How to Open Edit Interactions in Power BI Desktop

Follow these steps to configure visual interactions:

1. Open your Power BI report in Power BI Desktop.
2. Navigate to the report page containing the visuals you want to configure.
3. Select the source visual that will initiate the interaction.
4. Open the Format tab on the Power BI Desktop ribbon.
5. Choose Edit interactions. The command's location or presentation may vary slightly by Power BI Desktop version.
6. Look for interaction controls displayed on the other visuals on the page.
7. Choose the appropriate interaction option for each target visual.
8. Repeat the configuration for other source visuals as required.
9. Select Edit interactions again to exit interaction-editing mode.
10. Test the report by selecting different data points and checking the results.

Note: Edit interactions configures how visuals affect one another on a report page. It does not replace data modeling, relationships, or report-level filter configuration.

7. Interaction Options in Power BI

When Edit interactions is enabled, Power BI displays available controls for each target visual. Depending on the visual combination, these generally allow you to filter, highlight, or prevent the source visual from affecting the target.

7.1 Filter

The Filter option makes the target visual display data restricted by the selection made in the source visual.

Example: Selecting the East region in a region chart causes a product table to show products and sales for East only.

Use Filter when:

• Users need to examine a specific subset of data.
• Unrelated categories should be excluded from the target visual.
• The target visual needs to display detailed records for the selected category.

7.2 Highlight

The Highlight option emphasizes the portion associated with the selection while preserving the broader context where the target visual supports cross-highlighting.

Example: Selecting a region highlights its contribution in a product-sales chart while leaving other regions visible for comparison.

Use Highlight when:

• Users need to compare a selected contribution against the total.
• The overall data distribution should remain visible.
• Showing context is more important than hiding unselected data.

7.3 None

The None option disables the interaction from the selected source visual to a particular target visual. Selecting data in the source visual will not filter or highlight that target through that visual interaction.

Example: A company-wide KPI card is intended to display the same total regardless of which region is selected in a chart. Setting the chart-to-card interaction to None prevents that chart selection from changing the card.

Use None when:

• A visual should remain independent of a particular chart selection.
• A reference chart should always display the full comparison.
• A visual has a separate analytical purpose and should not respond to the source visual.

Important: None disables the specific visual interaction being configured. It does not necessarily make the target visual immune to slicers, page filters, report filters, or other filter sources.

7.4 Summary of Interaction Options

8. Managing Cross-Filtering Between Two Charts

Cross-filtering between charts is one of the most common Power BI interaction patterns.

8.1 Example: Region and Product Sales

Suppose a report includes a region chart and a product chart. The region chart displays sales by region, and the product chart displays sales by product.

1. Select the region chart.
2. Enable Edit interactions.
3. Locate the interaction controls on the product chart.
4. Select Filter if the product chart should display only the selected region's results.
5. Alternatively, select Highlight if the visual supports highlighting and users should compare the selected region with the overall product totals.
6. Select None if the product chart should remain unchanged by region selections.
7. Exit Edit interactions and test several regions.

8.2 Expected Behavior

The exact appearance depends on the chart types, measures, data model, and available interaction behavior.

9. Managing Interactions Between Charts and Cards

Cards are frequently used to display key performance indicators such as total sales, profit, quantity sold, or number of customers. Whether a card should respond to chart selections depends on its purpose.

9.1 Dynamic KPI Cards

A dynamic KPI card updates when a user selects a category in another visual.

For example, a total-sales card may display overall sales before a selection and then display only the selected region's sales after a region is selected.

To configure this behavior:

1. Select the chart that will initiate the interaction.
2. Enable Edit interactions.
3. Locate the interaction control on the KPI card.
4. Keep filtering enabled if the card should respond to the selection.
5. Exit Edit interactions and test the card.

9.2 Fixed Reference Cards

A fixed reference card is intended to provide a consistent benchmark, such as company-wide sales or an annual target. You may choose None for the interaction from a particular chart so that the chart's selections do not change the card.

However, the card may still respond to other slicers and filters. If the card must remain independent of additional filters, its measure and filter context may also need to be designed accordingly.

10. Managing Interactions Between Charts and Tables

Tables and matrices provide detailed information about records, categories, and measures. Interactions from charts to tables are useful for moving from a visual summary to supporting detail.

10.1 Example: Sales Summary and Transaction Details

A report contains a sales-by-category chart and a transaction table with customer, product, date, and sales amount.

1. Select the sales-by-category chart.
2. Enable Edit interactions.
3. Find the interaction control on the transaction table.
4. Choose Filter so that selecting a category restricts the table to matching records.
5. Exit Edit interactions.
6. Select different categories and verify that the table displays the expected records.

10.2 Best Practices for Tables

• Use filtering when users need record-level details for a selected category.
• Disable interactions that create irrelevant or confusing table results.
• Check that the table's fields and measures are appropriate for the selected context.
• Use clear column names and sensible sorting.
• Confirm that totals and subtotals are interpreted correctly after filtering.

11. Managing Slicer Interactions

Slicers are interactive controls that allow users to filter a report by fields such as date, region, product, customer, or department.

Slicers commonly affect multiple visuals, but the desired behavior can vary. For example, a date slicer may need to filter the main sales charts while leaving a separate benchmark visual unaffected by that slicer interaction.

11.1 Configuring a Slicer

1. Add a slicer to the report page and assign a field, such as Year or Region.
2. Select the slicer.
3. Enable Edit interactions.
4. Review the available interaction controls on the other visuals.
5. Keep the interaction enabled for visuals that should respond to the slicer.
6. Choose None for a visual that should not be affected by this slicer, if that option is available.
7. Exit Edit interactions and test the slicer.

11.2 Slicer Interaction Example

Use this setup carefully. A visual excluded from a slicer may show a broader time period than the other visuals, so its title or subtitle should make the difference clear.

12. Cross-Filtering and Data Model Relationships

Visual interactions depend not only on Edit interactions settings but also on the underlying data model. Relationships determine how filters propagate between related tables.

12.1 Role of Relationships

Consider a model containing a Sales table and a Product table. The Sales table contains ProductID, Quantity, and SalesAmount, while the Product table contains ProductID, ProductName, and Category.

A relationship between Product[ProductID] and Sales[ProductID] allows a category selection to filter related sales rows when the relationship and model are configured correctly.

12.2 Example Data Model

Product
-------
ProductID
ProductName
Category

Sales
-----
SalesID
ProductID
OrderDate
Quantity
SalesAmount

In this example, ProductID connects the product information with sales transactions. If the relationship is missing, inactive, ambiguous, or configured incorrectly, the expected filtering behavior may not occur.

12.3 Model Checks

• Verify that the required relationship exists.
• Confirm that the correct columns are used in the relationship.
• Check the relationship's cardinality and active status.
• Review cross-filter direction when filter propagation is unexpected.
• Avoid unnecessary bidirectional relationships because they can introduce ambiguity or unexpected filtering.
• Use a well-structured star schema when appropriate for analytical reporting.

Important distinction: Edit interactions controls communication between report visuals. Model relationships control how filters propagate between tables. Changing one does not automatically fix problems in the other.

13. Interaction Behavior and DAX Measures

DAX measures are evaluated in a filter context. When a visual interaction changes the filters applied to a visual, the measure may return a different result.

13.1 Example Sales Measure

Total Sales = SUM(Sales[SalesAmount])

If a user selects a region and the selection filters the Sales table, the Total Sales measure returns the sales amount for that region, assuming the model and interaction allow the filter to reach the relevant data.

13.2 Example Profit Measure

Total Profit = SUM(Sales[Profit])

This measure calculates total profit within the current filter context. It can respond to selections from charts, slicers, and other filters.

13.3 Example Profit Margin Measure

Profit Margin =
DIVIDE(
    [Total Profit],
    [Total Sales],
    0
)

The Profit Margin measure recalculates under the current filter context. Using DIVIDE helps avoid a division-by-zero error and returns the specified alternate result when the denominator is zero.

13.4 Why a Visual May Not Change

A visual may appear unaffected by a selection for several reasons:

• The interaction is set to None.
• The selected field does not filter the target visual's data through the model.
• The DAX measure deliberately removes filters using functions such as ALL or REMOVEFILTERS.
• The visual uses data that is unrelated to the selected field.
• The selected category does not have matching records in the target visual.

When investigating an unexpected result, inspect the interaction settings, relationships, fields, and measure definitions rather than assuming that Edit interactions is the only cause.

14. Clearing Selections and Restoring the Original View

After exploring a report, users may want to return to the unfiltered view.

14.1 Common Ways to Clear a Selection

• Select the currently selected data point again when the visual supports toggling off the selection.
• Click an appropriate blank area of the visual or report canvas where supported.
• Use the visual's clear-selection behavior, if available.
• Clear or reset slicers using their available controls.
• Use a report reset or bookmark-based reset experience if the report author has provided one.

The precise behavior depends on the visual and the report configuration. A selection in one visual may remain active even after another visual is selected.

14.2 Report Design Recommendation

For reports with many interactions, provide a clear way to reset the analysis. A reset button can use a bookmark that restores the intended default state, provided the bookmark is configured to capture the necessary filters and selections.

15. Interaction Settings Across Report Pages

Edit interactions primarily configures visual-to-visual behavior on the current report page. It should not be confused with navigation, drill-through, page-level filters, or report-level filters.

15.1 Understanding the Differences

A chart selection is not the same as navigating to another page. If users need a dedicated detail page, drill-through or page navigation may be more appropriate than relying only on cross-filtering.

16. Practical Example: Sales Performance Report

This exercise demonstrates how to configure cross-filtering and visual interactions in a sales report.

16.1 Required Data

Use a sales dataset with fields similar to the following:

16.2 Create the Measures

Total Sales = SUM(Sales[SalesAmount])

Total Profit = SUM(Sales[Profit])

Total Customers = DISTINCTCOUNT(Sales[CustomerID])

Profit Margin =
DIVIDE([Total Profit], [Total Sales], 0)

Adjust the table and column names to match your dataset. If customer information is stored in a separate table, use the appropriate model and customer identifier.

16.3 Build the Report Page

1. Add a card displaying Total Sales.
2. Add a card displaying Total Profit.
3. Add a column chart showing Total Sales by Region.
4. Add a bar chart showing Total Sales by Product.
5. Add a line chart showing Total Sales by Month.
6. Add a table containing Product, Region, Total Sales, and Total Profit.
7. Add a slicer for Year.

16.4 Configure Visual Interactions

These settings are examples, not universal defaults. Choose them according to the analytical purpose of each visual.

16.5 Test the Report

1. Select the North region and verify that the intended target visuals update.
2. Select a product and confirm that the detail table responds appropriately.
3. Change the Year slicer and verify that the visuals show the expected period.
4. Check that any visual configured with None remains unaffected by that specific source interaction.
5. Clear selections and verify that the report returns to its expected default state.
6. Compare card values with the underlying data to ensure that totals are correct.

17. Common Problems and Troubleshooting

17.1 Selecting a Chart Does Not Update Another Visual

Possible causes:

• The source-to-target interaction is set to None.
• The source and target visuals use unrelated fields or tables.
• A relationship is missing or inactive.
• The DAX measure removes the relevant filter context.
• The selected category has no matching records in the target visual.

Solutions:

1. Select the source visual and open Edit interactions.
2. Check the interaction control on the target visual.
3. Confirm that Filter or Highlight is selected as appropriate.
4. Inspect model relationships and the fields used by both visuals.
5. Review DAX measures for filter-removal logic.
6. Test using a category known to have matching records.

17.2 A Visual Displays Unexpectedly Low Values

Possible causes:

• A chart selection is filtering the visual to a subset of the data.
• Multiple slicers or filters are active.
• The visual is affected by another visual's selection.
• The measure is being evaluated under an unexpected filter context.

Solutions:

• Clear active selections and slicers.
• Review visual-, page-, and report-level filters.
• Check the interaction settings of relevant source visuals.
• Compare the result with a simple table or card using the same measure.

17.3 A Reference Chart Changes When It Should Remain Fixed

Possible cause: The reference chart is receiving an interaction from another visual.

Solution: Select the source visual, enable Edit interactions, and set its interaction with the reference chart to None where appropriate. Remember that other filters and slicers may still affect the reference chart.

17.4 Highlighting Is Not Available

Possible cause: The target visual or the particular visual combination does not support cross-highlighting.

Solution: Use the available Filter or None option, or choose compatible visual types if highlighting is an important requirement.

17.5 A Slicer Affects Only Some Visuals

Possible causes:

• The slicer's interaction with certain visuals is disabled.
• The visuals rely on disconnected or unrelated tables.
• The data model does not propagate the filter as expected.

Solutions:

1. Select the slicer and open Edit interactions.
2. Check its interaction with each relevant visual.
3. Review relationships and the fields used by the slicer.
4. Test the slicer with a simple visual based on a related field.

17.6 Totals Differ Between a Card and a Table

Possible causes:

• The card and table have different filters.
• The table is grouped by fields that change the measure's evaluation context.
• The DAX measure uses different aggregation logic than expected.
• One visual is intentionally excluded from an interaction.

Solutions:

• Compare the filter settings for both visuals.
• Check the DAX measures and aggregation logic.
• Verify whether the card is intended to show a filtered or overall total.
• Document intentional differences in the report.

18. Best Practices for Managing Visual Interactions

• Define the purpose of every visual: Decide whether it should show a filtered result, highlight a contribution, or remain independent.
• Use filtering for focused analysis: Apply Filter when users need to examine only the selected category.
• Use highlighting for comparisons: Choose Highlight when retaining the context of the overall dataset is useful and supported.
• Use None selectively: Disable interactions that do not support the report's analytical goal.
• Avoid unnecessary interaction complexity: Too many changing visuals can make reports confusing.
• Use clear titles: Indicate whether a chart shows all data or results for a selected category.
• Check the data model: Ensure that relationships support the expected filter flow.
• Validate DAX measures: Confirm that filter context produces meaningful results.
• Test with different selections: Test individual categories, multiple slicers, and cleared selections.
• Provide a reset option: Help users return to the default report state.
• Keep accessibility in mind: Use clear labels and do not rely only on color to communicate a highlighted selection.
• Consider performance: Complex models, expensive measures, and many visuals may slow interaction responses.
• Explain exceptions: If a visual intentionally ignores a selection, use an appropriate title or subtitle to prevent misinterpretation.

19. Cross-Filtering and Visual Interactions: Important Distinctions

20. Practice Exercises

Exercise 1: Configure Region-to-Product Filtering

Create a region chart and a product chart. Configure the region chart to filter the product chart. Select several regions and confirm that the product results change correctly.

Exercise 2: Compare Filtering and Highlighting

Use two compatible chart visuals to compare Filter and Highlight behavior. Record whether unrelated categories disappear or remain visible, and explain how each behavior affects interpretation.

Exercise 3: Create an Independent KPI

Add a Total Sales card and a region chart. Configure the card to ignore the region chart's selection. Verify that it remains unaffected by that chart interaction, and then test how slicers affect it.

Exercise 4: Configure a Detail Table

Create a sales chart and a transaction table. Configure the chart to filter the table, then test whether the selected category returns the correct transactions.

Exercise 5: Test Slicer Interactions

Add a Year slicer to a report page. Configure different interaction behavior for the sales charts and a reference visual. Confirm that the result is clear to users.

Exercise 6: Troubleshoot an Unexpected Result

Choose a visual that does not respond as expected. Check Edit interactions, relationships, slicers, filters, and DAX measures. Write down the cause and the steps used to correct the issue.

21. Interview Questions and Answers

Q1. What is cross-filtering in Power BI?

Cross-filtering is an interaction in which a selection in one visual restricts the data displayed in another visual to the matching selection context.

Q2. What is cross-highlighting?

Cross-highlighting emphasizes the selected portion of data in another visual while preserving broader context where the visual supports that behavior.

Q3. What is Edit interactions?

Edit interactions is a Power BI Desktop feature that lets report authors configure how one visual affects other visuals on the same report page.

Q4. What are the common interaction options?

The common options are Filter, Highlight, and None. The available options depend on the visual combination.

Q5. What is the difference between Filter and Highlight?

Filter restricts the target visual to the selected data context. Highlight emphasizes the selected contribution while retaining other data for comparison where supported.

Q6. What does None do in Edit interactions?

None disables the interaction from the selected source visual to the target visual. Other slicers and filters may still affect the target.

Q7. How do you configure visual interactions?

Select the source visual, open the Format tab, choose Edit interactions, configure the controls shown on target visuals, and exit the editing mode.

Q8. Why might a chart selection not affect another visual?

The interaction may be disabled, the fields may be unrelated, a model relationship may be missing, or a DAX measure may remove the relevant filter context.

Q9. Can a card ignore a chart selection?

Yes. The chart-to-card interaction can be set to None where the option is available. However, the card can still respond to other filters and slicers.

Q10. Does Edit interactions change model relationships?

No. Edit interactions controls visual-to-visual behavior, whereas model relationships define how filters propagate between tables.

Q11. Why is cross-highlighting unavailable for some visuals?

Not every visual type or visual combination supports cross-highlighting. Power BI provides the interaction options supported for the selected combination.

Q12. How can you troubleshoot unexpected card values?

Check active selections, slicers, visual interactions, filter settings, model relationships, and the DAX measure's filter-context behavior.

Q13. What is the difference between a slicer and Edit interactions?

A slicer is a report control users operate to filter data. Edit interactions configures how that slicer or another visual affects other visuals.

Q14. Why should interaction behavior be tested before publishing?

Testing confirms that selections produce expected values, visual exceptions are understandable, and users can explore the report without misleading results.

Q15. Can Edit interactions prevent every filter from affecting a visual?

No. It controls the configured interaction from a particular source visual. Other slicers, page filters, report filters, and model-level behavior may continue to affect the target.

22. Quick Revision Checklist

• Understand the difference between cross-filtering and cross-highlighting.
• Identify source and target visuals.
• Know how to open Edit interactions in Power BI Desktop.
• Use Filter to restrict the target visual to the selected context.
• Use Highlight to compare selected contributions where supported.
• Use None to disable a specific source-to-target interaction.
• Verify relationships between the relevant data tables.
• Review DAX measures when results do not respond as expected.
• Check slicers and visual-, page-, and report-level filters.
• Test multiple selections and reset behavior.
• Use titles and labels to explain intentionally independent visuals.
• Validate the report before publishing or sharing it.

23. Conclusion

Managing cross-filtering, visual interactions, and Edit interactions is essential for building clear, useful, and interactive Power BI reports. Cross-filtering helps users focus on a selected subset of data, while cross-highlighting preserves context for comparison when supported. Edit interactions gives report authors control over how individual visuals respond to selections from other visuals.

Effective interaction design requires more than choosing Filter, Highlight, or None. Report authors must also understand data model relationships, DAX filter context, slicer behavior, and the purpose of each visual. By configuring interactions carefully and testing different selections, you can create Power BI reports that support reliable analysis and better business decisions.

24. Additional Learning Resources

• Explore Microsoft Power BI Training at JustAcademy
• Register for a JustAcademy Course Demo
• Visit the JustAcademy Website
• Microsoft Learn: Change How Visuals Interact in a Power BI Report
• Microsoft Learn: Understand Model Relationships in Power BI Desktop
• Microsoft Learn: Data Analysis Expressions (DAX)